WHAT

🤖 Generated by Copilot at ae5cd23

The pull request refactors the code for making and handling API calls in the Facility components to use the request utility and the useQuery hook. It also adds and modifies type definitions for the requests and the responses for various API endpoints in src/Redux/api.tsx and src/Components/Facility/models.tsx. The purpose of these changes is to improve the code readability, performance, and type safety.
The pull request partially refactors the codebase for managing facility module in the frontend. It replaces the redux actions and states with the custom request function and the useQuery hook for data fetching and updating. It improves the code quality, performance, and readability by removing unnecessary imports, variables, and dependencies.

This pull request makes the required changes to only 3 files and does not close the entire issue.

Proposed Changes

• Part of 🛠️ Replace useDispatch w. useQuery/request: Facility (Part 2, E-H) (src/Components/Facility/[E-H]*.tsx) #6391
• Replaced useDispatch with request in FacilityCard.
• Replaced useDispatch with useQuery and request in FacilityCard and FacilityHome

@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers

Merge Checklist

• Add specs that demonstrate bug / test a new feature.
• Update product documentation.
• Ensure that UI text is kept in I18n files.
• Prep screenshot or demo video for changelog entry, and attach it to issue.
• Request for Peer Reviews
• Completion of QA

HOW

🤖 Generated by Copilot at ae5cd23

• Refactor API calls to use request utility and useQuery hook for fetching and caching data from the API endpoints (F0,F1,F2)
• Remove unused imports of useDispatch, statusType, useAbortableEffect, and action creators from ./src/Components/Facility/FacilityCard.tsx, ./src/Components/Facility/FacilityHome.tsx, and ./src/Components/Facility/FacilityUsers.tsx (link,link,link)
• Add imports of request, routes, and useQuery from ./src/Redux/api.tsx to ./src/Components/Facility/FacilityCard.tsx, ./src/Components/Facility/FacilityHome.tsx, and ./src/Components/Facility/FacilityUsers.tsx (link,link,link)
• Remove declarations of dispatch and dispatchAction from FacilityCard and FacilityHome components as they are no longer used for making API calls (link,link)
• Modify handleNotifySubmit function in FacilityCard component to use request utility instead of dispatchAction function to send notification messages to the facility, using routes.sendNotificationMessages object to define the API endpoint and the types, and destructuring res and data from the response object (link)
• Modify fetchData function in FacilityHome component to use useQuery hook instead of dispatch function to fetch the data for the facility, the capacity, the doctor, and the triage, using routes object to define the API endpoints and the types, and destructuring res, data, and refetch from the objects returned by the hook (link)
• Move fetchData function inside the useEffect hook that runs when the permittedFacilityRes changes, instead of using the useAbortableEffect hook that runs when the fetchData function changes, and remove the useAbortableEffect hook as it is no longer needed (link)
• Modify handleDeleteSubmit function in FacilityHome component to use request utility instead of dispatch function to delete the facility, using routes.deleteFacility object to define the API endpoint and the types, and passing id as a pathParams property to the request utility (link)
• Modify handleUpdate function in FacilityHome component to use capacityFetch and doctorFetch functions instead of dispatch function to refetch the capacity and doctor data, using the functions returned by the useQuery hook that handles the fetching and caching of the data from the API endpoints (link,link,link,link)
• Remove isLoading and setIsLoading from FacilityUsers component as they are no longer needed for handling the loading state of the data fetching (link)
• Modify fetchFacilityName function in FacilityUsers component to use request utility instead of dispatch function to fetch the facility name and district id, using routes.getAnyFacility object to define the API endpoint and the types, and passing id as a pathParams property to the request utility (link)
• Remove fetchData function from FacilityUsers component as it is no longer needed for fetching the facility users data, and use useQuery hook instead, using routes.getFacilityUsers object to define the API endpoint and the types, passing offset, limit, and facility_id as query and pathParams properties to the hook, setting prefetch property to facilityId !== undefined, and setting onResponse property to a function that updates the users and totalCount state variables with the data from the response (link)
• Modify loadFacilities function in FacilityUsers component to use request utility instead of dispatch function to fetch the facilities for a given user, using routes.userListFacility object to define the API endpoint and the types, and passing username as a pathParams property to the request utility (link)
• Modify handleUnlinkFacilitySubmit function in FacilityUsers component to use request utility instead of dispatch function to unlink a facility from a user, using routes.deleteUserFacility object to define the API endpoint and the types, and passing facility as a body and username as a pathParams property to the request utility (link)
• Modify handleSubmit function in FacilityUsers component to use request utility instead of dispatch function to delete a user, using routes.deleteUser object to define the API endpoint and the types, and passing username as a pathParams property to the request utility (link)
• Modify linkFacilitySubmit function in FacilityUsers component to use request utility instead of dispatch function to link a facility to a user, using routes.addUserFacility object to define the API endpoint and the types, and passing facility as a body and username as a pathParams property to the request utility (link)
• Remove isLoading variable from the condition to render the manageUsers component, and remove loading prop from the CountCard component, as they are no longer needed for handling the loading state of the data fetching (link,link)
• Add types for IFacilityNotificationRequest, IFacilityNotificationResponse, DeleteModel, and IUserFacilityRequest to ./src/Components/Facility/models.tsx (link)
• Add imports of CapacityModal, DoctorModal, PatientStatsModel, IFacilityNotificationRequest, IFacilityNotificationResponse, IUserFacilityRequest, and DeleteModel to ./src/Redux/api.tsx (link)
• Add TRes property to routes.getUser, routes.deleteUser, routes.getFacilityUsers, routes.deleteFacility, routes.getCapacity, routes.listDoctor, and routes.getTriage objects to define the type for the response for the API endpoints to get a user by username, to delete a user by username, to get the users for a facility, to delete a facility by id, to get the capacity for a facility, to get the doctor for a facility, and to get the triage for a facility, respectively (link,link,link,link,link,link,link)
• Add TBody and TRes properties to routes.addUserFacility, routes.deleteUserFacility, and routes.sendNotificationMessages objects to define the types for the request and the response for the API endpoints to link a facility to a user, to unlink a facility from a user, and to send notification messages to a facility, respectively (link,link,link)
• Modify path property of routes.deleteUser and routes.deleteFacility objects to include the {username} and {id} parameters as part of the API endpoint path, respectively (link,link)